Wagering game account management system

ABSTRACT

A wagering game account management system and its operations are described herein. In embodiments, the operations include determining that a trigger condition for an account rule has occurred, wherein the account rule specifies an account action to be performed upon satisfaction of the trigger condition, and wherein the account action is associated with a wagering game account and other financial accounts. In some embodiments, the operations also include initiating the account actions and indicating a result of the account actions.

RELATED APPLICATIONS

This application claims the priority benefit of U.S. ProvisionalApplication Ser. No. 60/865,057 filed Nov 9, 2006.

LIMITED COPYRIGHT WAIVER

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patentdisclosure, as it appears in the Patent and Trademark Office patentfiles or records, but otherwise reserves all copyright rightswhatsoever. Copyright 2006, WMS Gaming, Inc.

FIELD

Embodiments of the inventive subject matter relate generally to wageringgame systems, and more particularly to wagering game account managementsystems.

BACKGROUND

Wagering game machines, such as slot machines, video poker machines andthe like, have been a cornerstone of the gaming industry for severalyears. Generally, the popularity of such machines depends on thelikelihood (or perceived likelihood) of winning money at the machine andthe intrinsic entertainment value of the machine relative to otheravailable gaming options. Where the available gaining options include anumber of competing wagering game machines and the expectation ofwinning at each machine is roughly the same (or believed to be thesame), players are likely to be attracted to the most entertaining andexciting machines. Shrewd operators consequently strive to employ themost entertaining and exciting machines, features, and enhancementsavailable because such machines attract frequent play and hence increaseprofitability to the operator. Therefore, there is a continuing need forwagering game machine manufacturers to continuously develop new gamesand gaming enhancements that will attract frequent play.

SUMMARY

A machine-readable medium including instructions executable by amachine, the instructions including instructions to present a graphicaluser interface (GUI) that includes graphical representations of one ormore game session accounts and other accounts, wherein the one or moregame session accounts and other accounts are associated with a wageringgame player; instructions to detect an account selection via the GUI,the account selection to indicate the wagering game account or one ofthe other accounts; instructions to present, in the GUI, a graphicalrepresentation of transaction options associated with the accountselection; and instructions to detect, via the GUI, a request to performa transaction, the detection based on input associated with thegraphical representation of transaction options.

In some embodiments, each of the one or more game session accounts isassociated with a different wagering game, and wherein each differentwagering game is presented in the GUI at the same time.

In some embodiments, each of the one or more game session accounts isassociated with a different wagering game, and the instructions furtherinclude instructions to determine, based on the one or more game sessionaccounts, which of the different wagering games has awarded the mostmoney; and instructions to present a message in the GUI indicating theone of the different wagering games has awarded the most money.

In some embodiments, the graphical representation of transaction optionsincludes icons, and wherein the input indicates drag-and-drop operationsinvolving the icons and the graphical representation of the wageringgame account.

In some embodiments, the instructions further are comprisinginstructions to transmit the request to perform a transaction; andinstructions to present an indication that the transaction wassuccessfully completed.

In some embodiments, the wagering game account includes monetary valueavailable for use in placing a wager on a wagering game.

In some embodiments, the other accounts include one or more of achecking account, savings account, charity account, and educationaccount.

A method comprising determining that a trigger condition for an accountrule has occurred, wherein the account rule specifies an account actionto be performed upon satisfaction of the trigger condition, and whereinthe account action is associated with a wagering game account and otherfinancial accounts; initiating the account actions; and indicating aresult of the account actions.

In some embodiments, the wagering game account includes monetary valueavailable as credits on a wagering game machine.

In some embodiments, the account actions prohibit some financialtransactions for a specified duration.

In some embodiments, the account actions specify a financial transactioninvolving the wagering game account and one or more of the otherfinancial accounts.

In some embodiments, the initiating account actions includes contactinga financial institution computer associated with one or more of theother financial accounts.

In some embodiments, the trigger condition is based on results of awagering game.

In some embodiments, the trigger condition is selected from the set oftrigger conditions comprising a time, a balance of the wagering gameaccount, a balance of one of the other financial accounts, and an amountwagered in a wagering game.

In some embodiments, the method is further comprising transmitting anindication of the account rule in a format suitable for presentation ina graphical user interface; detecting a request to modify the accountrule, wherein the request indicates changes to at least one of thetrigger condition and the account action; modifying the account rulebased on the request.

A system comprising a wagering game machine including, an accountmanager configured to present a graphical user interface (GUI) includingmenus for creating an account rule, wherein the account rule specifies afinancial transaction associated with a wagering game account and otherfinancial accounts, and wherein the account rule specifies a conditionthat when satisfied will cause initiation of the financial transaction;an external system interface configured to transmit the account rule;and a wagering game unit configured to present wagering games; anaccount controller configured to receive the account rule and toinitiate the financial transaction upon satisfaction of the condition.

In some embodiments, the account controller is further configured todetect when the financial transaction is complete and to transmit anotification that the financial transaction is complete to the wageringgame machine.

In some embodiments, the wagering game account is associated with a gamesession, and wherein the balance of the wagering game account appears ina credit meter that is visible during the wagering games.

In some embodiments, the financial transaction is a transfer of fundsbetween the wagering game account and one of the other financialaccounts.

In some embodiments, the wagering game is further configured to notifythe account manager about results of the wagering games, and wherein thecondition is based on the results.

In some embodiments, the wagering game unit is further configured to usethe wagering game account as a direct source of monetary value forwagers that are placed on the wagering games.

In some embodiments, the condition indicates an amount of winnings.

BRIEF DESCRIPTION OF THE FIGURES

The present invention is illustrated by way of example and notlimitation in the Figures of the accompanying drawings in which:

FIG. 1 is a block diagram illustrating account transactions, accordingto example embodiments of the invention;

FIG. 2 is a block diagram illustrating a wagering game machinearchitecture, according to example embodiments of the invention;

FIG. 3 is a block diagram illustrating a wagering game network 300,according to example embodiments of the invention;

FIG. 4 is a flow diagram illustrating operations for facilitatingaccount transactions on a wagering game machine through a userinterface, according to example embodiments of the invention;

FIG. 5A is a block diagram illustrating a graphical user interfacethrough which players can request account transactions from a wageringgame machine, according to example embodiments of the invention;

FIG. 5B is a block diagram illustrating account information in awagering game machine's graphical user interface, according to exampleembodiments of the invention;

FIG. 6 is a flow diagram illustrating operations for processing accounttransactions made at a wagering game machine, according to exampleembodiments of the invention;

FIG. 7 is a flow diagram illustrating operations for presenting anaccount rule interface, according to example embodiments of theinvention;

FIG. 8 is a block diagram illustrating an account rules interface,according to example embodiments of the invention;

FIG. 9 is a block diagram illustrating an interface for configuringaccount rules, according to example embodiments of the invention;

FIG. 10 is a flow diagram illustrating operations for processing andstoring account rules, according to example embodiments of theinvention;

FIG. 11 is a flow diagram illustrating operations for enforcing accountrules in a wagering game system, according to example embodiments of theinvention; and

FIG. 12 is a perspective view of a wagering game machine, according toexample embodiments of the invention.

DESCRIPTION OF THE EMBODIMENTS

This description of the embodiments is divided into five sections. Thefirst section provides an introduction to embodiments of the invention,while the second section describes wagering game machine architecturesand wagering game networks. The third section describes interfaces andoperations of by some embodiments and the fourth section describesexample wagering game machines in more detail. The fifth sectionpresents some general comments.

Introduction

This section provides an introduction to some embodiments of theinvention.

Wagering game machines typically offer a limited number of ways forplayers to provide monetary value for use in wagering games. Somewagering game machines allow players to insert cash and cashlessvouchers or to draw from casino accounts. However, wagering gamemachines typically do not offer many other ways to procure funds. As aresult, when players run out of cash, cashless vouchers, and/or casinoaccount funds, they often leave the casino floor to acquire additionalfunds. For example, players may go to automated teller machines, banks,or other institutions from which they can procure funds. Someembodiments of the invention enable players to acquire funds from avariety of sources without leaving a wagering game machine.Additionally, some embodiments enable players to specify conditionsunder which various account transactions will take place. For example,players can create account rules that automatically replenish depletedaccounts, limit losses, donate a portion of winnings to charity, etc.The discussion of FIG. 1 describes some of these embodiments in moredetail.

FIG. 1 is a block diagram illustrating account transactions, accordingto example embodiments of the invention. In FIG. 1, a wagering gamemachine 102 is connected to an account controller 104, which isconnected to a financial institution computer 106. The wagering gamemachine 102 provides a graphical user interface 108 through whichplayers request account transactions and create account rules. Theaccount server 104 facilitates the account transactions and enforces theaccount rules, while the financial institution computer 106 alsofacilitates account transactions.

FIG. 1 shows two transactions. In the first transaction (see “1^(ST)” inFIG. 1) a player (not shown) uses the interface 114 to request transferof $500 from a checking account 114 to a game session account 110. Afterthe wagering game machine 102 receives the player's request, the machine102 notifies the account controller 104 about the request. As a result,the account controller 104 contacts the financial institution computer106, which transfers $500 from the player's checking account 114 to theplayer's game session account 110. Funds in the game session account 110appear on the wagering game machine's credit meter 118 and are availablefor use in wagering games presented on the wagering game machine 102.

In the second transaction (see “2^(ND)” in FIG. 1), the playerconfigures an account rule in the user interface 108. The account ruleprompts transfer of $20 from the player's game session account 110 tohis §529 account 116 for every $100 won playing wagering games. Forinformation about §529 accounts, see section 529 of the United StatesCode, which governs Qualified State Tuition Programs. The wagering gamemachine 102 notifies the account controller 104 about the account rule.The wagering game machine 102 also notifies the account controller 104whenever the player wins money playing wagering games. When the player'swinnings reach $100, the account controller 104 transfers $20 from thegame session account 110 to the §529 account 116. The account controller104 can support other account rules. In some embodiments, account rulescan transfer a percentage of winnings from the game session account 110to the §529 account 116. For example, if a player wins ten cents in asingle game, twenty percent (two cents) is transferred into the §529account 116.

Although FIG. 1 describes some embodiments, the following sectionsdescribe many other features and embodiments.

Example Operating Environment

This section describes an example operating environment and providesstructural aspects of some embodiments. This section includes discussionabout wagering game machine architectures and wagering game networks.

Wagering Game Machine Architecture

FIG. 2 is a block diagram illustrating a wagering game machinearchitecture, according to example embodiments of the invention. Asshown in FIG. 2, the wagering game machine architecture 200 includes awagering game machine cabinet 206, which includes a central processingunit (CPU) 226 connected to main memory 228. The CPU 226 can include anysuitable processor, such as an Intel® Pentium III processor, Intel® Core2 Duo processor, AMD Opteron™ processor, UltraSPARC processor, etc. Themain memory 228 includes a wagering game unit 232 and an account manager236. In some embodiments, the wagering game unit 232 can presentwagering games, such as video poker, video black jack, video slots,video lottery, etc., in whole or part. In some embodiments, the accountmanager 236 provides a user interface through which players can requestaccount transactions and configure account rules. For example, playerscan request funds transfers between various accounts, such as gamesession accounts, checking accounts, savings accounts, §529 accounts,charity accounts, etc. The account rules can cause transfers and othertransactions to occur when specific conditions are met. For example,account rules can initiate funds transfers when players wager specificamounts, win specific amounts, play a specific number of wagering games,etc.

The CPU 226 is also connected to an input/output (I/O) bus 222, whichcan include any suitable bus technologies, such as an AGTL+ frontsidebus and a PCI backside bus. The I/O bus 222 is connected to a payoutmechanism 208, primary display 210, secondary display 212, value inputdevice 214, player input device 216, information reader 218, and storageunit 230. The player input device 216 can include the value input device214 to the extent the player input device 216 is used to place wagers.The I/O bus 222 is also connected to an external system interface 224,which is connected to external systems 204 (e.g., wagering gamenetworks).

In one embodiment, the wagering game machine 206 can include additionalperipheral devices and/or more than one of each component shown in FIG.2. For example, in one embodiment, the wagering game machine 206 caninclude multiple external system interfaces 224 and/or multiple CPUs226. In one embodiment, any of the components can be integrated orsubdivided.

Any component of the architecture 200 can include hardware, firmware,and/or machine-readable media including instructions for performing theoperations described herein. Machine-readable media includes anymechanism that provides (i.e., stores and/or transmits) information in aform readable by a machine (e.g., a wagering game machine, computer,etc.). For example, tangible machine-readable media includes read onlymemory (ROM), random access memory (RAM), magnetic disk storage media,optical storage media, flash memory machines, etc. Machine-readablemedia also includes any media suitable for transmitting software over anetwork.

While FIG. 2 describes example embodiments of a wagering game machinearchitecture, FIG. 3 shows how a plurality of wagering game machines canbe connected in a wagering game network.

Wagering Game Network

FIG. 3 is a block diagram illustrating a wagering game network 300,according to example embodiments of the invention. As shown in FIG. 3,the wagering game network 300 includes a plurality of casinos 312connected to a communications network 314.

Each of the plurality of casinos 312 includes a local area network 316,which may include a wireless access point 304, wagering game machines302, and a wagering game server 306 that can serve wagering games overthe local area network 316. The wagering game server 306 includes anaccount controller 318, which can facilitate account transactions andenforce account rules. The account controller 318 can communicate withother network components, such as the financial institution computer324, when enforcing account rules and processing transactions. Also, theaccount controller 318 can record, modify, and use account informationin the account store 320 and rule store 322. In some embodiments, theaccount controller 328, account store 320, and the rule store 322 can belocated outside the casino 312.

The local area network 316 includes wireless communication links 310 andwired communication links 308. The wired and wireless communicationlinks can employ any suitable connection technology, such as Bluetooth,802.11, Ethernet, public switched telephone networks, SONET, USB,arcnet, current loop, etc. In one embodiment, the wagering game server306 can serve wagering games and/or distribute content to deviceslocated in other casinos 312 or at other locations on the communicationsnetwork 314.

Any of the wagering game network components (e.g., the wagering gamemachines 302) can include hardware and machine-readable media includinginstructions for performing the operations described herein.

The wagering game machines 302 described herein can take any suitableform, such as floor standing models, handheld mobile units, bartopmodels, workstation-type console models, etc. Further, the wagering gamemachines 302 can be primarily dedicated for use in conducting wageringgames, or can include non-dedicated devices, such as mobile phones,personal digital assistants, personal computers, etc. In one embodiment,the wagering game network 300 can include other network devices, such asaccounting servers, wide area progressive servers, player trackingservers, and/or other devices suitable for use in connection withembodiments of the invention.

In various embodiments, wagering game machines 302 and wagering gameservers 306 work together such that a wagering game machine 302 may beoperated as a thin, thick, or intermediate client. For example, one ormore elements of game play may be controlled by the wagering gamemachine 302 (client) or the wagering game server 306 (server). Game playelements may include executable game code, lookup tables, configurationfiles, game outcome, audio or visual representations of the game, gameassets or the like. In a thin-client example, the wagering game server306 may perform functions such as determining game outcome or managingassets, while the wagering game machine 302 may be used merely topresent the graphical representation of such outcome or assetmodification to the user (e.g., player). In a thick-client example, gameoutcome may be determined locally (e.g., at the wagering game machine302) and then communicated to the wagering game server 306 for recordingor managing a player's account.

Similarly, functionality not directly related to game play may becontrolled by the wagering game machine 302 (client) or the wageringgame server 306 (server) in embodiments. For example, accounttransactions and account rules may be managed centrally (e.g., by thewagering game server 306) or locally (e.g., by the wagering game machine302). Other functionality not directly related to game play may includepower management, presentation of advertising, software or firmwareupdates, system quality or security checks, etc.

Operations and Interfaces

This section describes operations and interfaces associated with someembodiments of the invention. In the discussion below, the flow diagramswill be described with reference to the block diagrams presented above.In certain embodiments, the operations are performed by executinginstructions residing on machine-readable media (e.g., software), whilein other embodiments, the operations are performed by hardware and/orother logic (e.g., firmware). In some embodiments, the operations areperformed in series, while in other embodiments, one or more of theoperations can be performed in parallel. Furthermore, the discussionbelow describes communications between wagering game network components.In some embodiments, the communications can include HyperText TransportProtocol (HTTP) requests for Hypertext Markup Language (HTML) documents.However, in other embodiments, the communications can be formattedaccording to different communication protocols.

The section will discuss FIGS. 4-11. FIGS. 4-6 will describe operationsand interfaces for performing account transactions in response to playerinput. The discussion of FIGS. 7-11 will describe operations andinterfaces for configuring account rules and performing accounttransactions based on the account rules.

Account Transactions

FIG. 4 is a flow diagram illustrating operations for facilitatingaccount transactions on a wagering game machine through a userinterface, according to example embodiments of the invention. The flowdiagram 400 will be described with reference to the FIG. 3's wageringgame network and FIG. 2's wagering game architecture. The flow begins atblock 402.

At block 402, a wagering game machine 302 detects a player identifier.The wagering game machine 302 may detect the player identifier as aresult of a player swiping a player account card, manually entering theidentifier, or providing some other device that indicates the playeridentifier (e.g., an RFID tag). The flow continues at block 404.

At block 404, the wagering game machine 302 receives a list of wageringgame accounts and other accounts associated with the player identifier.In some embodiments, the wagering game machine's account manager 236requests and receives the list from the account controller 318. The flowcontinues at block 406.

At block 406, the wagering game machine 302 presents a graphicalrepresentation of the wagering game accounts and/or other accountsenumerated in the list. For example, the wagering game machine's accountmanager 236 presents, on the primary display 210, a user interfaceincluding graphics that represent financial accounts associated with theplayer identifier. FIG. 5A shows one such user interface.

FIG. 5A is a block diagram illustrating a graphical user interfacethrough which players can request account transactions from a wageringgame machine, according to example embodiments of the invention. In FIG.5A, the graphical user interface 500 appears on a wagering gamemachine's touchscreen 502. As shown, the user interface 500 includesgraphics representing accounts associated with a player identifier. Thegraphics include a game session account icon 504, savings account icon506, casino account icon 508, §529 account icon 510, and money marketaccount icon 512. The GUI 500 can show icons for any number of financialaccounts. The accounts can include a game session account, casinodebit/credit accounts, checking accounts, savings accounts, educationalsavings accounts (e.g., a §529 account), charity accounts (e.g.,accounts that aid responsible gaming programs), holiday savingsaccounts, etc. According to embodiments, players can request accounttransactions by interacting with the icons.

Referring back to FIG. 4, the flow continues at block 408.

At block 408, the wagering game machine 302 detects a request forinformation about the wagering game account and/or other accounts. Forexample, the account manager 236 detects that a player has activated anicon in the user interface. The flow continues at block 410.

At block 410, the wagering game machine 302 receives account informationassociated with the account access request. The account information caninclude an account balance, transaction options associated with theaccount, and other information related to the account. In someembodiments, the account manager 236 requests and receives the accountinformation from the account controller 318. Flow continues at block412.

At block 412, the wagering game machine presents a graphicalrepresentation of the account information. To illustrate this concept,FIG. 5B shows how some embodiments can present account informationincluding transaction options in a GUI.

FIG. 5B is a block diagram illustrating account information in awagering game machine's graphical user interface, according to exampleembodiments of the invention. Players can activate the account icons bypressing the touchscreen 502. After an account icon is activated, theinterface 500 presents additional account transaction options, which arerepresented by additional icons. In FIG. 5B, the player 518 hasactivated the savings account icon 506. As a result, the interface 500has presented a savings account balance 520 and currency icons 514,which allow the player 518 to transfer different denominations between asavings account and other accounts. As shown, the player 518 is dragginga $20 currency icon 516 into the game session account icon 504. Thisdrag-and-drop operation constitutes a request to transfer $20 from theplayer's savings account into the player's game session account. The GUI500 supports similar drag-and-drop operations to request othertransfers. In some gaming jurisdictions, gaming regulations require thatplayers first transfer monies into casino accounts before transferringthose monies into game session accounts. The interface 500 can beconfigured to enforce/comply with gaming regulations, while alsofacilitating the account transactions described herein.

Referring back to FIG. 4, the flow continues at block 414.

At block 414, the wagering game machine 302 detects a transactionassociated with the account options. For example, the account manager236 detects a drag-and-drop operation that signifies an accounttransaction request. The drag-and-drop operations can indicate allparameters needed to request an account transaction. For example,drag-and-drop operations can indicate a transaction type, sourceaccount, destination account, currency amount, etc. The flow continuesat block 416.

At block 416, the wagering game machine 302 transmits an indication ofthe transaction request, so the wagering game account and/or otheraccounts can be adjusted. For example, the account unit 236 transmits,to the account controller 318, an indication of the transactions thatthe player requested via the user interface. From block 416, the flowends.

Although not explicitly described above, the account configurationoperations and features work for wagering game machines that can presentmultiple wagering games simultaneously. FIG. 5C illustrates thisconcept. FIG. 5C is a block diagram illustrating an interface thoughwhich players can perform account transactions associated with aplurality of game session accounts, according to some embodiments of theinvention. In FIG. 5C, a touch screen 530 includes an interface 532 thatis divided into four sections 534, 536, 538, and 540. The interface 532includes a slots game in section 534, blackjack in section 536, slots insection 538, and Texas Hold 'Em in section 540. Each game is associatedwith a separate game session account and a separate game session accountindicator 542. Some embodiments of the invention enable players totransfer funds between separate game session accounts and otheraccounts.

In FIG. 5C, the interface 532 includes a checking account icon 544,casino account icon 546, §529 account icon 548, and savings account icon550. The interface also includes a checking account balance indicator552 and currency icons 554, which allow the player 556 to transferdifferent denominations between a savings account and other accounts. Asshown, the player 556 is dragging a $20 currency icon 554 into the gamesession account icon 542. This drag-and-drop operation constitutes arequest to transfer $20 from the player's savings account into one ofthe player's game session accounts. The player 556 can transfer moniesinto any of the separate game session accounts by performing similardrag-and-drop operations. In some gaming jurisdictions, gamingregulations require that players first transfer monies into casinoaccounts before transferring those monies into game session accounts.The interface 532 can be configured to enforce/comply with gamingregulations, while also facilitating the account transactions describedherein.

Embodiments that support separate game session accounts can includelogic for evaluating a player's performance at multiple games. Forexample, a wagering game machine's account manager 236 can use theseparate game session accounts to determine: hold percentages associatedwith each game, games accumulating most winnings, games having mostlosses, etc. The account manager 236 can present this information in theinterface 500. For example, in FIG. 5C, the account manager 236 haspresented a message 558 stating, “Your Luckiest Game is Blackjack! ForBlackjack, You Are Up $50.”

Embodiments that support separate game session accounts can also enableplayers to play games in the background. For example, a player canselect a Keno game and transfer $100 into a game session accountassociated with the Keno game. The player can configure the Keno game toplay until the game session account has a zero balance. If the playerdoes not withdraw from the Keno game before the account has a zerobalance, the player's losses will be limited to the $100 transferred tothe game session account.

Thus far, this section has described account operations typicallyperformed by wagering game machines. This section will continue with adiscussion about account operations that are typically performed byaccount controllers.

FIG. 6 is a flow diagram illustrating operations for processing accounttransactions made at a wagering game machine, according to exampleembodiments of the invention. The flow 600 describes operations by whichan account controller transmits information to wagering game machines.In some embodiments, the wagering game machines include logic forpresenting the information (e.g., see discussion of FIG. 4). In otherembodiments (e.g., where the wagering game machine includes a thinclient) the account controller can control presentation of theinformation on the wagering game machines. The flow 600 begins at block602.

At block 602, the account controller 318 receives (from a wagering gamemachine 302) a request for a list of wagering game accounts and otherfinancial accounts associated with a player. The flow continues at block604.

At block 604, the account controller 318 transmits the account list tothe wagering game machine 302. As noted above, in some embodiments, theaccount controller 318 may control presentation of the account list onthe wagering game machine 302. The flow continues at block 606.

At block 606, the account controller 318 receives a request forinformation about the wagering game account and other accounts. Forexample, the request may ask for account balances, transaction options,information about recent transactions, etc. The flow continues at block608.

At block 608, the account controller 318 transmits the accountinformation to the wagering game machine 302. The flow continues atblock 610.

At block 610, the account controller 318 receives an account transactionrequest from the wagering game machine 302. For example, the accountcontroller 318 receives a request to transfer funds from the player'ssavings account to the player's game session account. The flow continuesat block 612.

At block 612, the account controller 318 adjusts the accounts based onthe transaction request. For example, the account controller 318instructs the financial institution computer 324 to deliver funds from asavings account to a game session account. In some embodiments, theaccount controller 318 does not transfer funds directly into gamesession accounts. Instead, the account controller 318 deposits fundsinto other wagering game accounts. Later, the account controller 318 cantransfer funds from the wagering game accounts to game session accounts,if needed. The flow continues at block 614.

At block 614, the account controller 318 provides account informationindicating the results of the requested transactions. For example, theaccount controller 318 notifies the player that funds have beentransferred between the player's savings account and game sessionaccount. The account controller 318 can notify the player by sending amessage to the wagering game machine 302. In some embodiments, thewagering game machine 302 will update its credit meter or other relatedbalances accordingly. From block 614, the flow ends.

Account Rules

This section continues with a discussion of account rules. Someembodiments enable players to submit rules that automatically initiateaccount transactions when certain conditions are met. In someembodiments, the account rules specify account transactions, source anddestination accounts, amounts, and trigger conditions. The accounttransactions can include transfers, deposits, withdrawals credits,debits, etc. When appropriate, source and destination accounts areidentified (e.g., for transfers). Trigger conditions indicate when rulesshould be enforced. Trigger conditions can relate to time, accountbalances, wagering game results, wagers placed, and any other statisticassociated with wagering game accounts, other financial accounts, andwagering games.

In some embodiments, players can use account rules to limit losses. Forexample, a player can create account rules that limit how much money canbe transferred from a checking account into a game session account.Alternatively, players can move a portion of each winning jackpot from agame session account into savings account, where the savings accountdoes not support wagering-game-related withdrawals. Players can alsocreate account rules that transfer percentages of winnings to fundsavings plans, charities, and other programs (e.g., responsible gamblingprograms). Furthermore, in some embodiments, players can create accountrules that, at the conclusion of a gaming session, automaticallytransfer the entire game session account balance to another account,such as a casino debit account, checking account, or the like. As aresult, embodiments eliminate the need for wagering game machines toreturn cash or cashless vouchers at the end of gaming sessions.

The following discussion will describe account rules in more details. Inparticular, the discussion of FIG. 7 will describe operations forpresenting an account rule interface, while the discussion of FIGS. 8 &9 will describe account rule interfaces. The discussion of FIGS. 10 & 11will cover operations for creating and enforcing account rules.

FIG. 7 is a flow diagram illustrating operations for presenting anaccount rule interface, according to example embodiments of theinvention. The flow 700 begins at block 702.

At block 702, a wagering game machine 302 presents an interface throughwhich players can view and configure account rules. In some embodiments,the account manager 236 and/or other components create the account ruleinterface and populate it with account information received from theaccount controller 318. In other embodiments, the machine 302 rendersthe account interface in a web browser, using information received fromthe account controller 318 or other network devices. FIG. 8 shows oneembodiment of an account rules interface.

FIG. 8 is a block diagram illustrating an account rules interface,according to example embodiments of the invention. In FIG. 8, theaccount rules interface 802 shows account rules currently affecting aplayer's financial accounts. The account rules interface 802 is dividedinto rows, where the rows show parameters for each account rule. Theparameters for each account rule (shown in row 806) include “ACTION”,“AMOUNT”, “SOURCE ACCOUNT”, “DESTINATION ACCOUNT”, and “TRIGGER”. Forexample, the row 808 shows an account rule that transfers $200 from theplayer's checking account to the player's casino account every day at12:00 am. Another rule, shown in row 812, transfers $100 from theplayer's casino account to the player's money market account when thecasino account is greater than $200. In addition to showing the accountrules, the account rules interface 802 includes a button 804 that canbring-up an interface for adding new rules. Although FIG. 8 shows anaccount rules interface in which players select from a predeterminedparameter values, other embodiments enable players to create accountrules by entering text (i.e., without a predetermined parameters) or byany other suitable method.

Referring back to FIG. 7, the flow continues at block 704.

At block 704, the wagering game machine 302 detects a change to theaccount rules. For example, the wagering game machine 302 detects that aplayer has attempted to create new rules or modify existing rules. Insome embodiments, players can create and modify rules as follows. In theembodiment of FIG. 8, players can modify existing rules by activating aparticular row in the interface 802 or by activating the button 804.After the player activates a row or the button 804, the wagering gamemachine 302 brings-up an interface for creating and modifying accountrules. FIG. 9 shows one such interface.

FIG. 9 is a block diagram illustrating an interface for creating andmodifying account rules, according to example embodiments of theinvention. In FIG. 9, the account rules interface 902 includes drop-downmenus for configuring account rule parameters. In particular, theinterface 902 includes an ACTION menu 904, AMOUNT menu 906, SOURCEACCOUNT menu 908, DESTINATION ACCOUNT menu 910, and a TRIGGER menu 912.Players can configure account rule parameters by selecting values fromthe menus 904-912. In some embodiments, when an existing rule is beingmodified, the menus 904-912 show the current parameter values.

Referring back to FIG. 7, the flow continues at block 706.

At block 706, the wagering game machine 302 submits the change to theaccount rules. Referring to FIG. 9, after a player has selected accountrule parameters in the menus 904-912, the player can press the button914 to submit the account rule for inclusion in the player's rule set.In some embodiments, the wagering game machine 302 submits the change bytransmitting an indication of the change to the account controller 318.From block 706, the flow ends.

Although wagering game machines can perform the operations of the flow700, in some embodiments, other devices perform those operations. Forexample, in a casino, players can use the kiosk 326 to view, create, andmodify their account rules. From outside the casino, players can view,create, and modify account rules using the workstation 328, which insome embodiments can communicate with the account controller 318 overthe world wide wed and/or the Internet. Account controllers can alsoplay a role in the process with which players view, create, and modifyaccount rules. This section continues with a discussion about howaccount servers can interact with a wagering game machine, kiosks, andworkstations to process and store account rules.

FIG. 10 is a flow diagram illustrating operations for processing andstoring account rules, according to example embodiments of theinvention. The flow diagram 1000 begins at block 1002.

At block 1002, the account controller 318 detects a request for accountrule information. In one embodiment, the account controller 318 receivesthe request from a wagering game machine 302 that is presenting theaccount rules interface 802. The account rule information can includeaccount rules associated with a player. The flow continues at block1004.

At block 1004, the account controller 318 transmits the account ruleinformation to the requester (e.g., a wagering game machine 302). Theaccount rule information can be in a form suitable for populating anaccount rules interface (e.g., see FIG. 8). The flow continues at block1006.

At block 1006, the account controller 318 detects a modification to theaccount rules associated with a player identifier. In some embodiments,the account controller 318 receives, from a wagering game machine 302, arequest to modify account rules associated with a player. The requestcan enumerate account rule parameters for a new account rule or for anexisting rule. The flow continues at block 1008.

At block 1008, the account controller 318 revises the account rulesaccordingly. For example, the account controller 318 modifies a player'saccount rules using the rule parameters received at block 1006. In someembodiments, the account controller 318 notifies the player that theaccount rules have been modified successfully or that there was an errorupdating the account rules. From block 1008, the flow ends.

This section continues with a discussion about operations for enforcingthe account rules.

FIG. 11 is a flow diagram illustrating operations for enforcing accountrules in a wagering game system, according to example embodiments of theinvention. The flow 1100 begins at block 1102.

At block 1102, the account controller 318 determines that a ruleassociated with a wagering game account should be enforced. As notedabove, account rules can be associated with trigger condition. Forexample, winning jackpots, placing wagers, playing certain games,account balances, time of day, total amount of wagers made, etc. cantrigger account rules to perform financial transactions. In someembodiments, the wagering game machines 302 notifies the to the accountcontroller 318 about any information relevant to a player's accountrules. For example, wagering game machines 302 can notify the accountcontroller 318 when a player wins a jackpot, makes a wager, plays agame, begins a game session, ends a game session, etc. In response, theaccount controller 318 can determine whether any account rules' triggerconditions have been satisfied. In other embodiments, the wagering gamemachines 302 can acquire a list of account rules and notify the accountcontroller 318 only when a trigger condition has been satisfied.

In some embodiments, account rules are not associated with wagering gameevents. For example, account rules can be related to time, accountbalances, account transactions, etc. Thus, the account controller 318can use time, account balances, account transactions, and othernon-event-related information to determine that an account rules shouldbe enforced. The flow continues at block 1104.

At block 1104, the account controller 318 performs transactionsspecified in the account rules that are being enforced. For example, ifan account rule specifies a transfer of funds, the account controller318 transfers funds between accounts. As another example, if the accountrule specifies that an account is to be locked, the account controller318 locks the account. As yet another example, if the account rulespecifies that certain transactions are prohibited (e.g., withdrawalsfrom a retirement account), the account controller 318 marks the accountas deposit only. The account controller 318 may enforce some accountrules with assistance from the financial institution computer 324. Theflow continues at block 1106.

At block 1106, the account controller 318 provides an indication of thefinancial transactions. In some embodiments, the account controller 318can transmit a transaction statement for display on the wagering gamemachine 302 at which the player is present (e.g., in an accountinterface). Alternatively, the account controller 318 can notify theplayer via email, instant message, telephone message, etc. From block1106, the flow ends.

Example Wagering Game Machines

FIG. 12 is a perspective view of a wagering game machine, according toexample embodiments of the invention. Referring to FIG. 12, a wageringgame machine 1200 is used in gaming establishments, such as casinos.According to embodiments, the wagering game machine 1200 can be any typeof wagering game machine and can have varying structures and methods ofoperation. For example, the wagering game machine 1200 can be anelectromechanical wagering game machine configured to play mechanicalslots, or it can be an electronic wagering game machine configured toplay video casino games, such as blackjack, slots, keno, poker,blackjack, roulette, etc.

The wagering game machine 1200 comprises a housing 1212 and includesinput devices, including value input devices 1218 and a player inputdevice 1224. For output, the wagering game machine 1200 includes aprimary display 1214 for displaying information about a basic wageringgame. The primary display 1214 can also display information about abonus wagering game and a progressive wagering game. The wagering gamemachine 1200 also includes a secondary display 1216 for displayingwagering game events, wagering game outcomes, and/or signageinformation. While some components of the wagering game machine 1200 aredescribed herein, numerous other elements can exist and can be used inany number or combination to create varying forms of the wagering gamemachine 1200.

The value input devices 1218 can take any suitable form and can belocated on the front of the housing 1212. The value input devices 1218can receive currency and/or credits inserted by a player. The valueinput devices 1218 can include coin acceptors for receiving coincurrency and bill acceptors for receiving paper currency. Furthermore,the value input devices 1218 can include ticket readers or barcodescanners for reading information stored on vouchers, cards, or othertangible portable storage devices. The vouchers or cards can authorizeaccess to central accounts, which can transfer money to the wageringgame machine 1200.

The player input device 1224 comprises a plurality of push buttons on abutton panel 1226 for operating the wagering game machine 1200. Inaddition, or alternatively, the player input device 1224 can comprise atouch screen 1228 mounted over the primary display 1214 and/or secondarydisplay 1216.

The various components of the wagering game machine 1200 can beconnected directly to, or contained within, the housing 1212.Alternatively, some of the wagering game machine's components can belocated outside of the housing 1212, while being communicatively coupledwith the wagering game machine 1200 using any suitable wired or wirelesscommunication technology.

The operation of the basic wagering game can be displayed to the playeron the primary display 1214. The primary display 1214 can also display abonus game associated with the basic wagering game. The primary display1214 can include a cathode ray tube (CRT), a high resolution liquidcrystal display (LCD), a plasma display, light emitting diodes (LEDs),or any other type of display suitable for use in the wagering gamemachine 1200. Alternatively, the primary display 1214 can include anumber of mechanical reels to display the outcome. In FIG. 12, thewagering game machine 1200 is an “upright” version in which the primarydisplay 1214 is oriented vertically relative to the player.Alternatively, the wagering game machine can be a “slant-top” version inwhich the primary display 1214 is slanted at about a thirty-degree angletoward the player of the wagering game machine 1200. In yet anotherembodiment, the wagering game machine 1200 can exhibit any suitable formfactor, such as a free standing model, bartop model, mobile handheldmodel, or workstation console model.

A player begins playing a basic wagering game by making a wager via thevalue input device 1218. The player can initiate play by using theplayer input device's buttons or touch screen 1228. The basic game caninclude arranging a plurality of symbols along a payline 1232, whichindicates one or more outcomes of the basic game. Such outcomes can berandomly selected in response to player input. At least one of theoutcomes, which can include any variation or combination of symbols, cantrigger a bonus game.

In some embodiments, the wagering game machine 1200 can also include aninformation reader 1252, which can include a card reader, ticket reader,bar code scanner, RFID transceiver, or computer readable storage mediuminterface. In some embodiments, the information reader 1252 can be usedto award complimentary services, restore game assets, track playerhabits, etc.

General

In this detailed description, reference is made to specific examples byway of drawings and illustrations. These examples are described insufficient detail to enable those skilled in the art to practice theinventive subject matter, and serve to illustrate how the inventivesubject matter can be applied to various purposes or embodiments. Otherembodiments are included within the inventive subject matter, aslogical, mechanical, electrical, and other changes can be made to theexample embodiments described herein. Features or limitations of variousembodiments described herein, however essential to the exampleembodiments in which they are incorporated, do not limit the inventivesubject matter as a whole, and any reference to the invention, itselements, operation, and application are not limiting as a whole, butserve only to define these example embodiments. This detaileddescription does not, therefore, limit embodiments of the invention,which are defined only by the appended claims.

Each of the embodiments described herein are contemplated as fallingwithin the inventive subject matter, which is set forth in the followingclaims.

1. A machine-readable medium including instructions executable by amachine, the instructions comprising: instructions to present agraphical user interface (GUI) that includes graphical representationsof one or more game session accounts and other accounts, wherein the oneor more game session accounts and other accounts are associated with awagering game player; instructions to detect an account selection viathe GUI, the account selection to indicate one of the one or more gamesession accounts or one of the other accounts; instructions to present,in the GUI, a graphical representation of transaction options associatedwith the account selection; and instructions to detect, via the GUI, arequest to perform a transaction, the detection based on inputassociated with the graphical representation of transaction options. 2.The machine-readable medium of claim 1, wherein each of the one or moregame session accounts is associated with a different wagering game, andwherein each different wagering game is presented in the GUI at the sametime.
 3. The machine-readable medium of claim 1, wherein each of the oneor more game session accounts is associated with a different wageringgame, the instructions further comprising: instructions to determine,based on the one or more game session accounts, which of the differentwagering games has awarded the most money; and instructions to present amessage in the GUI indicating the one of the different wagering gameshas awarded the most money.
 4. The machine-readable medium of claim 1,wherein the graphical representation of transaction options includesicons, and wherein the input indicates drag-and-drop operationsinvolving the icons and the graphical representation of the wageringgame account.
 5. The machine-readable medium of claim 1, theinstructions further comprising: instructions to transmit the request toperform a transaction; and instructions to present an indication thatthe transaction was successfully completed.
 6. The machine-readablemedium of claim 1, wherein the wagering game account includes monetaryvalue available for use in placing a wager on a wagering game.
 7. Themachine-readable medium of claim 1, wherein the other accounts includeone or more of a checking account, savings account, charity account, andeducation account.
 8. A method comprising: determining that a triggercondition for an account rule has occurred, wherein the account rulespecifies an account action to be performed upon satisfaction of thetrigger condition, and wherein the account action is associated with awagering game account and other financial accounts; initiating theaccount actions; and indicating a result of the account actions.
 9. Themethod of claim 8, wherein the wagering game account includes monetaryvalue available as credits on a wagering game machine.
 10. The method ofclaim 8, wherein the account actions prohibit some financialtransactions for a specified duration.
 11. The method of claim 8,wherein the account actions specify a financial transaction involvingthe wagering game account and one or more of the other financialaccounts.
 12. The method of claim 8, wherein the initiating accountactions includes contacting a financial institution computer associatedwith one or more of the other financial accounts.
 13. The method ofclaim 8, wherein the trigger condition is based on results of a wageringgame.
 14. The method of claim 8, wherein the trigger condition isselected from the set of trigger conditions comprising a time, a balanceof the wagering game account, a balance of one of the other financialaccounts, and an amount wagered in a wagering game.
 15. The method ofclaim 8, further comprising: transmitting an indication of the accountrule in a format suitable for presentation in a graphical userinterface; detecting a request to modify the account rule, wherein therequest indicates changes to at least one of the trigger condition andthe account action; modifying the account rule based on the request. 16.A system comprising: a wagering game machine including, an accountmanager configured to present a graphical user interface (GUI) includingmenus for creating an account rule, wherein the account rule specifies afinancial transaction associated with a wagering game account and otherfinancial accounts, and wherein the account rule specifies a conditionthat when satisfied will cause initiation of the financial transaction;an external system interface configured to transmit the account rule;and a wagering game unit configured to present wagering games; anaccount controller configured to receive the account rule and toinitiate the financial transaction upon satisfaction of the condition.17. The system of claim 16, wherein the account controller is furtherconfigured to detect when the financial transaction is complete and totransmit a notification that the financial transaction is complete tothe wagering game machine.
 18. The system of claim 16, wherein thewagering game account is associated with a game session, and wherein thebalance of the wagering game account appears in a credit meter that isvisible during the wagering games.
 19. The system of claim 16, whereinthe financial transaction is a transfer of funds between the wageringgame account and one of the other financial accounts.
 20. The system ofclaim 16, where the wagering game is further configured to notify theaccount manager about results of the wagering games, and wherein thecondition is based on the results.
 21. The system of claim 16, where thewagering game unit is further configured to use the wagering gameaccount as a direct source of monetary value for wagers that are placedon the wagering games.
 22. The system of claim 16, the conditionindicates an amount of winnings.